Update Codeowners, Issues, and Project automation #609
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: bmorelli25 <[email protected]>
bmorelli25
changed the title
bmorelli25
commented
May 9, 2025
georgewallace
requested changes
May 19, 2025
Contributor
georgewallace
left a comment
georgewallace
left a comment
There was a problem hiding this comment.
would like @shainaraskas and @szabosteve to review the changes to the groups. I think I got it right.
Co-authored-by: George Wallace <[email protected]>
Co-authored-by: shainaraskas <[email protected]> Co-authored-by: George Wallace <[email protected]>
bmorelli25
changed the title
Contributor
florent-leborgne
left a comment
florent-leborgne
left a comment
There was a problem hiding this comment.
Thanks! Experience docs is missing from a few places
Co-authored-by: florent-leborgne <[email protected]>
shainaraskas
approved these changes
May 20, 2025
Collaborator
shainaraskas
left a comment
shainaraskas
left a comment
There was a problem hiding this comment.
couple of mild quibbles
Comment on lines
+60
to
+62
| # Legacy serverless docs | ||
| /serverless/ @elastic/admin-docs | ||
| /serverless/serverless-changelog.asciidoc @elastic/docs |
Collaborator
There was a problem hiding this comment.
we can just delete these files, right?
georgewallace
approved these changes
May 20, 2025
Contributor
georgewallace
left a comment
georgewallace
left a comment
There was a problem hiding this comment.
Good with this once we add @shainaraskas feedback
Contributor
colleenmcginnis
left a comment
colleenmcginnis
left a comment
There was a problem hiding this comment.
Just a couple little suggestions.
Co-authored-by: shainaraskas <[email protected]> Co-authored-by: Colleen McGinnis <[email protected]>
Co-authored-by: shainaraskas <[email protected]>
Co-authored-by: Colleen McGinnis <[email protected]>
Member
Author
|
Thank you for all of your helpful suggestions 👥 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
How issues/triaging will work
If a writer opens an issue in their teams area, they are expected to remove the
needs-teamlabel and apply the appropriate docs team labels. For all other instances of issues opened, the assigned "on call" writer will triage issues by adding them to their teams product boards and fixing easy issues.